bba. inpadi GMS Core - Server side

inpadi GMS Core is the server side of the inpadi service and responsible for communication and scheduling.

GMS components communicates everything over a HTTPS tunnel and every job that a client carries out is AES-128 encrypted before it's send over HTTPS.

The scheduler in inpadi GMS Core do 3 things.

1. Move a ".que" schedule to "NextJob.txt" to be executed at the client

It looks for .que files if there is not a NextJob.txt file to the client. The .que file can have any name and in alphabetic order moved to NextJob.txt

2. Move a ".db" to ".que" (puts a scheduled job on the clients execution queue)

It looks for a .db file if the scheduled time has passed it will be moved to .que.

Syntax for creating a run once scheduled job is "YearMonthDay.HourMinute.DB" in the format "YYYYMMDD.HHMM.DB".

4. Move a ".db" to ".que" and create next schedule time for job

It looks for a .db file if the scheduled time has passed it will be moved to .que and it will create the next schedule time.

Syntax for creating a once scheduled job is "YearMonthDay.HourMinute.YearMonthDay.HourMinute.Minutes.DB" in the format "YYYYMMDD.HHMM.YYYYMMDD.HHMM.M.DB".

The first part "YYYYMMDD.HHMM" is when to start the job, the second part "YYYYMMDD.HHMM" is when the job must be completed and the last part "M" is the time to next scheduled run in minutes (1 Hour = 60, 1 Day = 1440, 1 Week = 10080).

For special commands and names see - "bca. inpadi GMS Guide to jobs and scripts".